Printed: Sep 28, 2024
From: http://jcp.org/en/jsr/detail?id=88
|
Specification Leads | |||
Gerald Ingalls | Oracle | ||
Expert Group | |||
BEA Systems | IBM | IBM/Websphere | |
iPlanet | Oracle | Progress Software | |
Silverstream Software | Skylight Systems, Inc. | Sun Microsystems, Inc. | |
Sybase | WebGain |
The following updates were made to the original request:
2005.11.01:
Maintenance Lead:Jerome Dochez
E-Mail Address: jerome.dochez
Telephone Number: +1 408 276 7062
Fax Number: +1 408 276 7191
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Sun Microsystems, Inc
Name of Contact Person: Rebecca Searls
E-Mail Address: rebecca.searls@east.sun.com
Telephone Number: (781) 442-0462
Fax Number: (781) 443-1610
Specification Lead: Rebecca Searls
E-Mail Address: rebecca.searls@east.sun.com
Telephone Number: (781) 442-0462
Fax Number: (781) 443-1610
Initial Expert Group Membership:
Skylight Systems
WebGain
Forte
Oracle
SilverStream
BEA
IBM
Verge Technologies Group Inc
IONA
iPlanet
Section 2: Request
The API will address the three-stage deployment process:
Java 2 Platform Enterprise Edition J2EE Product Providers currently implement their own proprietary deployment interface to their server because there is no standard deployment API. This makes it cumbersome for companies that host heterogeneous J2EE environments to deploy an application across multiple J2EE environments, because they must run the designated deploy tool for a given server. A standard deployment API will enable any J2EE application to be deployed by any deployment tool that uses the deployment APIs onto any J2EE compatible environment.
The Java 2 Platform Enterprise Edition Specification specifies a deployment file format and static deployment information descriptors. It does not, however, define a standard API for gathering dynamic deployment information that applies to application installation into the server, application configuration, or undeployment.
The Deployment Specification will support the existing deployment file format and static deployment information descriptors. In addition it will provide an interface for discovering additional information from J2EE servers which implement it. The interface will also enable tools to collect vendor specific dynamic information for installing, configuring and undeploying J2EE applications on the server. The API will encapsulate the common functions of different vendors' deployment process with a standardized Java interface.
No dependency on Java visual tools for constructing and deploying J2EE applications will be assumed by this API.
javax.deployment No. No. No. Future releases of the Java 2 Enterprise Edition Specification may require
revision in the area of deployment.
Section 3: Contributions
Java 2 Platform Enterprise Edition
Specification
The J2EE specification defines the deployment requirements, but does not
define specific APIs.
(Please provide company or organization names. Note that expert group
members must have signed the JSPA.)
Aaron Mulder amulder@skylightsystems.com
Mark Romano mark.romano@webgain.com
George Finklang george.fink@sun.com
Gerald Ingalls Gerald.Ingalls@oracle.com
Helen Herold hherold@silverstream.com
Mark Spotswood mark@bea.com>
Michael Fraenkel fraenkel@us.ibm.com
Jason Westra nim80302@yahoo.com
David Hayes dhayes@iona.com
Byron Nevins byron.nevins@sun.com
2.1 Please describe the proposed Specification:
This specification defines standard APIs that will enable any deployment
tool that uses the deployment APIs to deploy any assembled application
onto a J2EE compatible platform.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
2.3 What need of the Java community will be addressed by the proposed specification?
2.4 Why isn't this need met by existing specifications?
2.5 Please give a short description of the underlying technology or technologies:
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
2.8 Are there any security issues that cannot be addressed by the current security model?
2.9 Are there any internationalization or localization issues?
2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
2.11 Please describe the anticipated schedule for the development of this
specification.
Community Draft October 2001
Public Draft December 2001
Proposed Final Draft February 2002
Final Release Aligned with J2EE 1.4 Platform Spec Final Release
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.
3.2 Explanation of how these items might be used as a starting point for the work.